Uplink channel reservation with conflicting wireless communications

ABSTRACT

Systems and methods presented herein provide for channel reservation for a wireless telephony system operating in an RF band with a wireless system comprising a conflicting wireless technology. One method is operable with an eNodeB. The method includes assigning an ID (e.g., a PN sequence) to a user equipment (UE) operating in the RF band, processing a scheduling request for uplink (UL) data from the UE, and granting a time and a frequency for the UE to transmit the UL data. The method also includes waiting until the UE performs a Listen Before Talk (LBT) operation to determine whether the granted time and frequency is occupied by another wireless system employing a different wireless technology. The method also includes transmitting the ID to the UE to reserve the granted time and frequency when unoccupied by the other wireless system, and processing the UL data from the UE.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to, and thus the benefit of anearlier filing date from, U.S. Provisional Patent Application No.62/161,443 (filed May 14, 2015), the entire contents of which are herebyincorporated by reference.

BACKGROUND

Cellular telephony continues to evolve at a rapid pace. Cellulartelephone networks currently exist in a variety of forms and operateusing a variety of modulations, signaling techniques, and protocols,such as those found in 3G and LTE networks (3rd Generation of mobiletelecommunications technology and Long Term Evolution, respectively). Asconsumers require more capacity, the networks usually evolve. Forexample, some carriers, or Mobile Network Operators (MNOs), employ acombination of 3G and the faster LTE because MNOs needed faster networksto satiate the increased demand for data and voice.

Moreover, efforts exist to implement these technologies in radiofrequency (RF) bands that comprise conflicting communications. Forexample, there has been accelerated development of LTE in unlicensedbands (a.k.a. LTE-U and Licensed-Assisted-Access, or “LAA-LTE”) whereWiFi has traditionally been implemented. Unlike LTE, however, WiFiemploys a method of Listen Before Talk (LBT) to ensure that WiFi systemsdo not interfere with one another. If LTE were to also employ LBT, itwould decrease the ability of user equipment (“UEs”, such as cellphonesand other mobile devices) to make uplink (UL) transmissions.

SUMMARY

Systems and methods presented herein provide for channel reservation fora wireless telephony system operating in an RF band with a wirelesssystem comprising a conflicting wireless technology. In one embodiment,a method is operable with an eNodeB operating in an RF band comprising aconflicting wireless technology. The method includes assigning an ID(e.g., a pseudorandom number, or “PN”) to a user equipment (UE)operating in the RF band, processing a scheduling request for uplink(UL) data from the UE, and granting a time and a frequency for the UE totransmit the UL data. The method also includes waiting until the UEperforms a Listen Before Talk (LBT) operation to determine whether thegranted time and frequency is occupied by another wireless systememploying a different wireless technology. The method also includestransmitting the ID to the UE to reserve the granted time and frequencywhen unoccupied by the other wireless system, and processing the UL datafrom the UE.

In another embodiment, a method is operable in a UE. The method includesprocessing an ID (e.g., a PN) assigned by an eNodeB, transmitting ascheduling request to the eNodeB for uplink (UL) data from the UE, andprocessing a time and frequency grant from the eNodeB for the UE totransmit the UL data. The method also includes waiting until the grantedtime and frequency are clear of another wireless system employing adifferent wireless technology operating in the RF band, and, when thegranted time and frequency are clear, transmitting the UL data to theeNodeB.

The various embodiments disclosed herein may be implemented in a varietyof ways as a matter of design choice. For example, some embodimentsherein are implemented in hardware whereas other embodiments may includeprocesses that are operable to implement and/or operate the hardware.Other exemplary embodiments, including software and firmware, aredescribed below.

BRIEF DESCRIPTION OF THE FIGURES

Some embodiments of the present invention are now described, by way ofexample only, and with reference to the accompanying drawings. The samereference number represents the same element or the same type of elementon all drawings.

FIG. 1 is a block diagram of an exemplary wireless telecommunicationssystem operating in an RF band with a conflicting wireless system.

FIG. 2 is a flowchart illustrating an exemplary process operable withthe eNodeB in the wireless telecommunications system.

FIG. 3 is a flowchart illustrating another exemplary process operablewith the eNodeB in the wireless telecommunications system.

FIG. 4 is a flowchart illustrating an exemplary process operable withthe UE in the wireless telecommunications system.

FIG. 5 is a flowchart illustrating another exemplary process operablewith the UE in the wireless telecommunications system.

FIG. 6 is an exemplary messaging diagram between a UE and an eNodeB inthe wireless telecommunications system.

FIG. 7 is another exemplary messaging diagram between a UE and an eNodeBin the wireless telecommunications system.

FIG. 8 is another exemplary messaging diagram between a UE and an eNodeBin the wireless telecommunications system.

FIG. 9 is an exemplary table of the QoS Class Identifiers.

FIG. 10 is a flowchart illustrating another exemplary process operablewith the wireless telecommunications system for determining an LBT timerbased on Quality of Service (QoS) Class Identifiers.

FIGS. 11A and 11B are flowcharts of an exemplary process operable withthe eNodeB in the wireless telecommunications system.

FIG. 12 is a flowchart of another exemplary process operable with the UEin the wireless telecommunications system.

FIG. 13 is a block diagram of an exemplary computing system in which acomputer readable medium provides instructions for performing methodsherein.

DETAILED DESCRIPTION OF THE FIGURES

The figures and the following description illustrate specific exemplaryembodiments of the invention. It will thus be appreciated that thoseskilled in the art will be able to devise various arrangements that,although not explicitly described or shown herein, embody the principlesof the invention and are included within the scope of the invention.Furthermore, any examples described herein are intended to aid inunderstanding the principles of the invention and are to be construed asbeing without limitation to such specifically recited examples andconditions. As a result, the invention is not limited to the specificembodiments or examples described below.

FIG. 1 is a block diagram of an exemplary wireless telecommunicationssystem operating in an RF band with a conflicting wireless system. Thewireless telecommunications system comprises an eNodeB 111communicatively coupled to a wireless telephony network 110. Generally,the eNodeB 111 is any system, apparatus, software, or combinationthereof operable to maintain or otherwise support wirelesscommunications, including data and voice, with subscribers via their UEs112 (e.g., mobile handsets and other wireless devices). In this regard,the eNodeB 111 may implement the wireless communications of the wirelesstelephony network 110 over RF via, for example, 2G, 3G, LTE, 5G, or thelike.

The conflicting wireless system comprises wireless access point (WAP)121 communicatively coupled to the wireless network 120. The wirelesssystem of the WAP 121 conflicts with the wireless telecommunicationssystem of the eNodeB 111 as the wireless system of the WAP 121 uses aform of wireless technology that is incompatible with the communicationprotocols of the wireless telecommunications system of the eNodeB 111.Thus, communications between the UE 112-2 and the WAP 121 can interferewith the communications between the UE 112-1 and the eNodeB 111.

To illustrate, the eNodeB 111 may be part of an LTE wireless telephonynetwork, whereas the WAP 121 may be part of a WiFi network (e.g., a WiFihotspot or a personal WiFi router). Generally, this means that theeNodeB 111 is operating in an unlicensed band of RF, such as theindustrial, scientific, and medical (ISM) band, where WiFicommunications have flourished. Because these bands are so clutteredwith WiFi communications, WiFi devices (e.g., the UE 112-2) employ LBTto ensure that they do not interfere with one another when operating viaWiFi. LTE communications, however, tend to occupy an entire band offrequencies at any given time to ensure that their communicationsbetween their UEs 112 can be sustained. Thus, at the very least, an LTEwireless telephony network will interfere with other communicationsystems in the band. So, to be more “friendly” with other wirelesssystems in an unlicensed band, the embodiments herein provide for LBToperations between the UE 112-1 and an eNodeB 111 of a wirelesstelephony network 110.

The media access control (MAC) of LTE uses a centralized scheduler wherethe eNodeB 111 schedules UL and downlink (DL) traffic. LBT generallydoes not present problems on LTE DL transmissions because the eNodeB 112transmits when it has successfully contended for a channel. ULtransmissions, however, are scheduled at precise instances of time andfrequency. And, LBT disrupts the timing of the scheduled ULtransmissions.

In LTE, the UE 112-1 transmits when the UE 112-1 has been granted a timeand frequency by the eNodeB 111. To be granted a time and frequency bythe eNodeB 111, the UE 112-1 schedules a request for a UL datatransmission, which may be done in various ways. For example, the UE112-1 may send a one bit indicator in a Scheduling Request (SR) when itneeds UL shared channel (SCH) resources. Alternatively or additionally,the UE 112-1 may transmit a Buffer Status Report (BSR) when the UE 112-1already has a valid scheduling grant so as to indicate its queue depthwith the BSR. Generally, the BSR is sent as part of the MAC header inthe payload such that the UE 112-1 can “piggyback” on the BSR when usingthe UL resource.

However, in the unlicensed RF band, the UE 112-1 needs to perform LBTbefore each UL transmission because the channel may not be clear at thetime of its scheduled transmission. LBT increases the uncertainty ofwhen the UE will get to transmit, and therefore increases the delayincurred on the UL data. When the UE 112-1 successfully contends for thechannel to transmit its data, the data may have already passed a delaybudget based on the LTE protocols and is discarded.

After the eNodeB 111 receives the SR, the eNodeB 111 starts a timer thatkeeps track of the elapsed time from the channel frequency/time grantresulting from the SR. When the timer elapsed passes a threshold delay,the eNodeB 111 starts monitoring the channel for the UE. When thechannel has cleared, the eNodeB 111 reserves the channel on behalf ofthe UE 112-1 by broadcasting a UE-specific ID to reserve the channel.Upon receiving the ID, the UE 112-1 immediately transmits its data, orwith a short delay. In one embodiment, the UE-specific ID is apseudorandom number (PN) sequence already assigned to each UE usedmainly during UE handover. This channel reservation can also beimplemented by piggybacking its indication of UL data on the BSR of theLTE protocol.

With this in mind, FIG. 2 is a flowchart illustrating an exemplaryprocess 200 operable with the wireless telecommunications systememploying the eNodeB 111. In this embodiment, the eNodeB 111 assigns anID to the UE 112-1 operating in the RF band of the eNodeB 111, in theprocess element 201. When the UE 112-1 needs to transmit UL data to theeNodeB 111, the UE 112-1 transmits an SR for UL data. In this regard,the eNodeB 111 processes the SR for UL data from the UE 112-1, in theprocess element 202. Based on a priority of the UL data, the eNodeB 111grants a time and frequency for the UE 112-1 to transmit its UL data tothe eNodeB 111, in the process element 203.

The eNodeB 111 starts a timer, in the process element 205, and thenperforms an LBT operation, in the process element 206, to determinewhether the channel is clear (i.e., at the granted time and frequency).If the channel is clear, the eNodeB 111 transmits the assigned ID to theUE 112-1 to reserve the granted time and frequency for the UE 112-1 totransmit its UL data, in the process element 208. Otherwise, the process200 ends, in the process element 207. For example, the UL data mayinclude high-priority voice data. However, the packetized UL data mayinclude a relatively small portion of speech in the UL communications tothe eNodeB 111. Accordingly, if a channel cannot be reserved before thetimer expires, the packetized data containing the speech may be droppedas it is no longer fresh, resulting in a negligible amount of lostspeech. And, if the UL 112-1 can transmit its UL data, the eNodeB 111processes the UL data from the UE 112-1, in the process element 209.

FIG. 3 is a flowchart illustrating another exemplary process 225operable with the eNodeB 111 in the wireless telecommunications system.The eNodeB 111 assigns an ID to the UE 112-1 operating in the RF band,in the process element 226. This allows the UE 112-1 to communicate withthe eNodeB 111. The eNodeB 111 processes a scheduling request for ULdata from the UE 112-1, in the process element 227. The eNodeB 111grants a time and frequency for the UE 112-1 to transmit the UL data, inthe process element 228. The eNodeB 111 starts a timer, in the processelement 229, to determine whether the UE 112-1 is able to transmit theUL data within the granted time and frequency.

If the timer expires, in the process element 230, then the eNodeB 111performs an LBT to determine whether the channel is clear, in theprocess element 235. If the timer has not expired, then the eNodeB 111determines if it has received the UL data from the UE 112-1, in theprocess element 231, and continues to check the timer, in the processelement 232, until the timer has expired (i.e., the process element230).

If the channel is clear, in the process element 235, then the eNodeB 111transmits the ID to the UE 112-1 to reserve the granted time frequency,in the process element 234. From there, the eNodeB 111 receives andprocesses the UL data from the UE 112-1, in the process elements 237 and238, and the process ends until the UE 112-1 needs to transmitadditional UL data. If the channel is not clear, then the eNodeB 111 mayattempt to perform another LBT, in the process element 236, otherwisethe process ends.

If the eNodeB 111 receives the UL data from the UE 112-1, in the processelement 231, then the eNodeB 111 processes the UL data from the UE112-1, in the process element 233 and the process ends, that is untilthe UE 112-1 needs to transmit additional UL data.

FIG. 4 is a flowchart illustrating another exemplary process 250operable with the wireless telecommunications system. In thisembodiment, the process 250 is illustrated with respect to the UE 112-1.Thus, the process 250 initiates with the UE 112-1 processing the IDassigned by the eNodeB 111, in the process element 251. The UE 112-1transmits the SR to the eNodeB 111 for scheduling transmission of its ULdata, in the process element 252. Once the eNodeB 111 grants a time andfrequency for its UL data of the UE 112-1, the UE 112-1 processes thetime and frequency grant from the eNodeB 111, in the process element253. The UE 112-1 then performs an LBT operation to determine whetherthe channel is clear, in the process element 254.

Once the channel clears, the UE 112-1 determines whether it has receivedthe ID to reserve the channel, in the process element 255. If so, the UE112-1 processes the ID assigned by the eNodeB 111, in the processelement 255, and the UE 112-1 then transmits the UL data to the eNodeB111, in the process element 256. If the ID is not received, then theprocess 250 ends until the UE 112-1 needs to transmit another block ofUL data. In this regard, the UE 112-1 may discard the UL data.

FIG. 5 is a flowchart illustrating another exemplary process 260operable with the UE 112-1 in the wireless telecommunications system. Inthis embodiment, the UE 112-1 processes the ID assigned by the eNodeB111, in the process element 261. The UE 112-1 transmits a schedulerequest to the eNodeB 111 for UL data from the UE 112-1, in the processelement 262. The UE 112-1 processes a time and frequency grant from theeNodeB 111 for the UE 112-1 to transmit UL data, in the process element263.

The UE 112-1 determines whether the channel is clear by performing anLBT process for a pre-determined time prior to granted time, in theprocess element 264. For example, the UE 112-1 may implement a timer.However, in processing for a predetermined time (t-n) prior to the granttime (t), a timer may not be necessary as the time window for eachprocess is already known. If the channel is clear, then the UE 112-1transmits the UL data, in the process element 265 and the process ends(i.e., until the UE 112-1 needs to transmit additional UL data). If thechannel is not clear, then the UE 112-1 determines whether the timefrequency grant has expired, in the process element 266. If the granthas not expired, then the UE 112-1 continues to determine whether thechannel is clear through the LBT process (i.e., process element 264).

If the time and frequency grant has expired, then the UE 112-1 starts atimer for a predetermined period, in the process element 267. Fromthere, the UE 112-1 determines whether it has received the ID from theeNodeB 111, in the process element 268. If the UE 112-1 has received theID from the eNodeB 111, then the UE 112-1 transmits the UL data to theeNodeB 111, in the process element 269, and the process ends (i.e.,until the UE 112-1 needs to transmit additional UL data).

If the UE 112-1 has not received the ID from the eNodeB 111 (i.e., theprocess element 268), then the UE 112-1 determines whether the timer hasexpired, in the process element 270, and continues to check whether ithas received the ID from the eNodeB 111 until the timer has expired. Ifthe timer has expired, then the UE 112-1 may drop the UL data, in theprocess element 271, and reschedule a request to transmit UL data, inthe process element 272. If the UE 112-1 determines that it needs toreschedule the UL data request, and the process 260 returns to theprocess element 262. Otherwise, the process 260 ends (i.e., until the UE112-1 needs to transmit additional UL data).

FIG. 6 is an exemplary messaging diagram between a UE 112 and an eNodeB111 in the wireless telecommunications system. Again, the UE 112 sendsan SR to the eNodeB 111 for scheduling transmission of the UL data. TheeNodeB 111, in turn, responds with a UL data transmission grant with adesignated time and frequency. The eNodeB 111 then starts a timer andwhile the UE 112-1 performs the LBT operation. The UL grant may alsoinclude the LBT timer which lets the UE 112 know how long it has todetermine whether the granted channel is clear of communications fromanother conflicting wireless system. Once the channel clears and thetimer has not expired, the eNodeB 111 transmits the assigned ID forchannel reservation such that the UE 112 can transmit its UL data.

FIG. 7 is another exemplary messaging diagram between a UE 112 and aneNodeB 111 in the wireless telecommunications system. This embodimentrepresents a messaging sequence in which the UE 112 fails LBT and the UE112-1 is unable to transmit UL data in the allocated time indicated bythe UL grant even though the eNodeB 111 successfully reserves thechannel after allocated time of the UL grant. The sequence begins withthe UE 112 transferring a UL data scheduling request. The eNodeB 111responds with a UL grant including a time, frequency, and an LBT timer.The UE 112 performs an LBT operation and the eNodeB 111 may start itstimer, with the end of the timer being set to expire after the expectedtransmission of UL data from the UE 112-1. However, this may not benecessary, as the eNodeB 111 generally knows when it should receive ULdata from the UE 112-1.

After the time expected for the UE 112 to transmit its data has expired,the UE 112 starts a timer, which substantially coincides with end of theeNodeB 111's timer. The eNodeB 111 performs an LBT operation and, if thechannel is clear, sends the ID to the UE 112 to reserve the channel.From there, the UE 112 is free to transmit its UL data. Sending the IDto the UE 112 to reserve the channel may be, for example a one-to-onecommunication, a one-to-many communication, a broadcast communication, amulti-hop relay communication, etc.

FIG. 8 is another exemplary messaging diagram between a UE 112 and aneNodeB 111 in the wireless telecommunications system. This embodimentrepresents where the UE 112 fails LBT and is unable to transmit UL datain the allocated time indicated by the UL grant. The embodiment alsoillustrates that the eNodeB 111 also fails the LBT and is thereforeunable to reserve the channel for the UE 112 after the allocated time ofthe UL grant. Thus, the sequence begins with the UE 112 transferring afirst UL scheduling request and the eNodeB 111 granting the request witha time, frequency, and an LBT timer for the UE 112.

Again, the UE 112 performs an LBT operation and the eNodeB 111 startsits timer. The sequence continues as with FIG. 7 until the eNodeB 111performs its LBT operation and determines that the channel is not clear.Then, the UE 112's timer expires and it drops the UL data. The UE 112may then send a second scheduling request to the eNodeB 111 to reattempttransmission of the UL data.

In one embodiment, the timer is a dynamically assigned by the eNodeB 111based on a QOS for the UE 112-1. For example, a UL scheduler of theeNodeB 111 in LTE communications traditionally schedules UL datatransmissions based on current loading of eNodeB 111, capability of theUE 112-1, cell capacity of the eNodeB 111, interference, resource block(RB) utilization at neighboring cells, etc. While those factors arestill considered, in this embodiment, the eNodeB 111 establishes andupdates the timer for each UE 112 communicating with the eNodeB 111based on their various traffic flows (a.k.a. bearer traffic). Toillustrate, each type of bearer traffic may have an associated QOS Classidentifier (QCI) that takes into consideration factors such as delay,jitter, guaranteed bit rate (GBR), non-GBR, etc. And, each UE 112 mayhave multiple forms of air traffic to transmit to the eNodeB 111.Examples of these QCIs are illustrated in the table 280 of FIG. 9.

With this in mind, FIG. 10 illustrates a flowchart of a process 290 ofthe eNodeB 111. The eNodeB 111 collects the bearer info for a UE 112, inthe process element 291, and determines the type of bearer traffic forthe UE 112, in the process element 292, as illustrated in FIG. 10. TheeNodeB 111 then determines whether the QCI of the bearer traffic beingpresented to the eNodeB 111 (e.g., through an SR to the eNodeB 111) hasa GBR, in the process element 293. If the bearer traffic has a GBR, thenthe eNodeB 111 sets the timer to a GBR threshold, in the process element294. Generally, this means that the bearer traffic is high-priority ULdata, such as conversational voice. Accordingly, the timer should be setto some minimal amount (e.g., as a matter of design choice) so as toquickly discard the UL data when it becomes stale in the event that thechannel is not clear. The eNodeB 111 then transfers the time andfrequency grant to the UE 111, in the process element 295, such that theUE 112 can perform the LBT operation to determine whether the channel isclear, as described above.

If the bearer traffic does not have a GBR, then the eNodeB 111determines other types of bearer traffic presented from other UEs 112currently assigned to the eNodeB 111, in the process element 296. Withthis information, the eNodeB 111 establishes a timer according to thebearer traffic of the other UEs 112, in the process element 297. Forexample, the types of bearer traffic that do not have a GBR may includenon-conversational video (e.g., buffered streaming video) where the ULdata can be saved/stored and transmitted over time as the delivery ofthat data is not time sensitive. The eNodeB 111 may collect informationfrom the other UEs 112 having bearer traffic to determine an aggregateQCI and arrive at a timer based on that aggregate QCI. Once the timerhas been computed, the eNodeB 111 transfers the time and frequency grantto the UE 111 (and other UEs 112 with bearer traffic assigned to theeNodeB 111), in the process element 295.

Additionally, when a UE 112-1 has multiple bearers (i.e., multiple typesof UL traffic), the UE 112-1 makes its own decisions on which bearertraffic to transmit first upon receiving a grant. In this regard, the UE112-1 prioritizes its traffic to transmit its most delay sensitivetraffic first. This is the reason for setting the timer to the delaybudget of the QCI with a stringent delay requirement among all of thetraffic bearers of the UE 112-1. But, when the UE 112 has only non-GBRbearers (e.g., non-time sensitive traffic), the eNodeB 111 can set thetimer to the system load by adjusting it according to, for example, a95th percentile delay of all the traffic bearers that the eNodeB 111serves to improve the QOS for the users

The MAC layer of the UE 112 is an intelligent entity that controlslogical channel multiplexing. Above the MAC layer is the Radio LinkControl (RLC) layer, where the traffic from different service bearersare segregated. In many cases, the MAC layer of the UE 112-1 commandsthe RLC to pull from each logical channel buffer based on various rules,including QOS requirements of the bearer.

For example, during initial deployments of LTE, multiple bearers,particularly those with different QCIs, were not widely used. However,as users of the UEs 112 have more applications and more types of data,multiple bearers need to be provisioned. And, as LTE moves into theunlicensed spectrum with implementations of LBT, the UE 112 can nolonger be in complete control of scheduling its own transmissionsbecause if a UE 112 schedules its UL data transmission based on thepriority of the bearer, higher priority bearers will always get servedfirst, and lower priority, non-GBR bearers may be “starved” oftransmission resources.

In these embodiments, the UE 112 now contends for a channel prior totransmission. Accordingly, in one embodiment, non-GBR traffic is sentfirst with the possibility of discarding GBR traffic altogether, as someGBR traffic can afford to miss transmissions. For example, a packet ofvoice conversation data that is dropped will generally only result in anegligible amount of lost speech.

To prioritize the data at the UE 112, the embodiments herein provide fora 2-bit priority indicator field added to the SR that indicates whetherthe SR has high priority data, low priority data, or a combinationthereof. This allows the eNodeB 111 to gain a granular control of the UE112 s scheduling mechanism. When the UE 112 has indicated both high andlow priority traffic in the SR, but the eNodeB 111 has only indicatedlow priority traffic in the grant, this is an indication that the highpriority traffic has passed (e.g., the timer has expired) such that theUL data can be discarded by the UE 112.

With this in mind, FIGS. 11A, 11B, and 12 illustrate exemplary processesof the wireless telecommunications system. More specifically, FIGS. 11Aand 11B are flowcharts of an exemplary process 300 operable with theeNodeB in the wireless telecommunications system, whereas FIG. 12 is aflowchart of an exemplary process 350 operable with the UE 112-1 in thewireless telecommunications system.

In FIG. 11A, the process 300 initiates when the eNodeB 111 assigns an ID(e.g., a PN sequence) to the UE 112-1, in the process element 301. TheeNodeB 111 then processes SRs for the first and second UL data, in theprocess elements 302 and 303. The eNodeB 111 then determines prioritiesof the first and second UL data, in the process element 304 and grants atime and frequency for the UE 112-1 to transmit the first and second ULdata, in the process element 305. The process 300 continues in FIG. 11B(via connection point “A”).

In FIG. 11B, the process 300 continues (via connection point “A”) withthe eNodeB 111 starting a timer, in the process element 306. The eNodeB111 may then determine whether the first UL data is stale, in theprocess element 307. If the first UL data is not stale, then the eNodeB111 continues its timer countdown, in the process element 308.

If the first UL data is stale, the eNodeB 111 may perform an LBToperation to determine whether the channel is clear, in the processelement 309. If the channel is clear, the eNodeB 111 transmits the ID tothe UE 112-1 to reserve the granted time and frequency for the UE 112-1(e.g., to transmit the second UL data), in the process element 311. Indoing so, the eNodeB 111 may also direct the UE 112-1 to discard thefirst UL data. And, the eNodeB 111 then processes the second UL datafrom the UE 112-1, in the process element 312, and the process 300 ends.If the channel is not clear, the eNodeB 111 may try again, in theprocess element 310. Otherwise, the process 300 ends.

In FIG. 12, the process 350 initiates by the UE 112-1 processing the IDassigned by the eNodeB 111, in the process element 351. The UE 112-1prioritizes the first and second UL data, in the process element 352,giving the first UL data higher priority than the second UL data. The UE112-1 then transmits SRs for the first and second UL data, in theprocess element 353. Upon receiving the grants for time and frequencyfrom the eNodeB 111, the UE 112-1 performs an LBT operation, in theprocess element 354, to determine whether the channel is clear.

If the channel is not clear, then the UE 112-1 determines whether thefirst UL data has expired, in the process element 355. For example, theeNodeB 111 establishes a timer for the higher priority data such that itcan be discarded by the UE 112-1 when that data becomes stale. If thefirst UL data has not expired, then the UE 112-1 continues determiningwhether the channel is clear (i.e., the process element 354). Once thechannel clears (and the first UL data has not expired), then the UE112-1 transmits the first UL data and the lower priority second UL datato the eNodeB 111, in the process element 357. Otherwise, when the firstUL data expires (i.e., process element 355), the UE 112-1 discards thefirst UL data, in the process element 356. The UE 112-1 may, however,still transmit the lower priority second UL data, in the process element357.

Discarding of the first UL data may be at the direction of the eNodeB111 or based on a timer maintained by the UE 112-1. In any case, thefirst UL data is discarded as it is no longer needed, as in the casewith conversational voice dropping a packet of voice data that isnegligible to the overall conversation.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In one embodiment, the invention is implementedin software, which includes but is not limited to firmware, residentsoftware, microcode, etc. FIG. 10 illustrates a computing system 400 inwhich a computer readable medium 406 may provide instructions forperforming any of the methods disclosed herein.

Furthermore, the invention can take the form of a computer programproduct accessible from the computer readable medium 406 providingprogram code for use by or in connection with a computer or anyinstruction execution system. For the purposes of this description, thecomputer readable medium 406 can be any apparatus that can tangiblystore the program for use by or in connection with the instructionexecution system, apparatus, or device, including the computer system400.

The medium 406 can be any tangible electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system (or apparatus ordevice). Examples of a computer readable medium 406 include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Some examples of optical disksinclude compact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD.

The computing system 400, suitable for storing and/or executing programcode, can include one or more processors 402 coupled directly orindirectly to memory 408 through a system bus 410. The memory 408 caninclude local memory employed during actual execution of the programcode, bulk storage, and cache memories which provide temporary storageof at least some program code in order to reduce the number of timescode is retrieved from bulk storage during execution. Input/output orI/O devices 404 (including but not limited to keyboards, displays,pointing devices, etc.) can be coupled to the system either directly orthrough intervening I/O controllers. Network adapters may also becoupled to the system to enable the computing system 400 to becomecoupled to other data processing systems, such as through host systemsinterfaces 412, or remote printers or storage devices throughintervening private or public networks. Modems, cable modem and Ethernetcards are just a few of the currently available types of networkadapters.

What is claimed is:
 1. A method operable with an eNodeB operating in aradio frequency (RF) band comprising a conflicting wireless technology,the method comprising: assigning an identification (ID) to a userequipment (UE) operating in the RF band; receiving a scheduling requestfor uplink (UL) data from the UE; granting to the UE a time and afrequency for the UE to transmit the UL data based on the receivedscheduling request; determining, after performance of a first ListenBefore Talk (LBT) operation by the UE, that the granted time andfrequency are occupied by another wireless system employing a differentwireless technology; starting a timer, within which the UE performs asecond LBT operation; transmitting, prior to expiration of the timer andafter reception of a clear channel assessment based on the second LBToperation, the assigned ID to the UE to reserve the granted time andfrequency when unoccupied by the other wireless system; and processingthe UL data from the UE.
 2. The method of claim 1, wherein: the otherwireless system is a WiFi system.
 3. The method of claim 1, furthercomprising: determining a quality of service (QoS) of the UE;establishing the timer based on the QoS; and dropping the UL data whenthe timer expires to process another scheduling request for UL data fromthe UE.
 4. The method of claim 1, wherein: the eNodeB communicates tothe UE via Long Term Evolution (LTE) communications.
 5. The method ofclaim 1, wherein: the ID is a pseudorandom number sequence.
 6. A methodoperable with a user equipment (UE) operating in a radio frequency (RF)band comprising a conflicting wireless technology, the methodcomprising: transmitting a scheduling request to an eNodeB for uplink(UL) data from the UE; processing a time and frequency grant from theeNodeB for the UE to transmit the UL data; performing a first ListenBefore Talk (LBT) operation; determine, from the first LBT operation,that the granted time and frequency are occupied by another wirelesssystem employing a different wireless technology operating in the RFband; executing a second LBT operation to verify that the granted timeand frequency are not occupied by the other wireless system; sending aclear channel acknowledgment to the eNodeB based the second LBToperation; receiving an identification (ID), from the eNodeB, reservingthe granted time and frequency; and broadcasting, after the step ofreceiving, the UL data to the eNodeB.
 7. The method of claim 6, furthercomprising: discarding the UL data at the direction of the eNodeB basedon a timer established by the eNodeB.
 8. The method of claim 6, wherein:the other wireless system is a WiFi system.
 9. The method of claim 6,wherein: the ID is a pseudorandom number sequence.
 10. The method ofclaim 6, wherein: the UE broadcasts the UL data to the eNodeB via LongTerm Evolution (LTE) communications.
 11. An eNodeB operating in a radiofrequency (RF) band comprising a conflicting wireless technology, theeNodeB comprising: a processor operable to (i) assign an identification(ID) to a user equipment (UE) operating in the RF band, (ii) process ascheduling request for uplink (UL) data from the UE, (iii) grant a timeand a frequency for the UE to transmit the UL data, (iv) start a timerafter providing to the UE the UL grant, and (v) receive a clear channelacknowledgement from the UE based on an a Listen Before Talk (LBT)operation performed by the UE to determine, before an expiration of thetimer, whether the granted time and frequency are occupied by anotherwireless system employing a different wireless technology; and aninterface operable to transmit the ID to the UE to reserve the grantedtime and frequency when unoccupied by the other wireless system, and toreceive the UL data from the UE on the granted time and frequency. 12.The eNodeB of claim 11, wherein: the other wireless system is a WiFisystem.
 13. The eNodeB of claim 11, wherein: the processor is furtheroperable to determine a quality of service (QoS) of the UE, to establishthe timer based on the QoS, and to drop the UL data when the timerexpires to process another scheduling request for UL data from the UE.14. The eNodeB of claim 11, wherein: the eNodeB communicates to the UEvia Long Term Evolution (LTE) communications.
 15. The eNodeB of claim11, wherein: the ID is a pseudorandom number sequence.